Word-processing document stored in a single XML file that may be manipulated by applications that understand XML

ABSTRACT

A word processor including a native XML file format is provided. The well formed XML file fully represents the word-processor document, and fully supports 100% of word-processor&#39;s rich formatting. There are no feature losses when saving the word-processor documents as XML. A published XSD file defines all the rules behind the word-processor&#39;s XML file format. Hints may be provided within the XML associated files providing applications that understand XML a shortcut to understanding some of the features provided by the word-processor. The word-processing document is stored in a single XML file. Additionally, manipulation of word-processing documents may be done on computing devices that do not include the word-processor itself.

BACKGROUND OF THE INVENTION

Markup Languages have attained wide popularity in recent years. One type of markup language, Extensible Markup Language (XML), is a universal language that provides a way to identify, exchange, and process various kinds of data. For example, XML is used to create documents that can be utilized by a variety of application programs. Elements of an XML file have an associated namespace and schema.

In XML, a namespace is a unique identifier for a collection of names that are used in XML documents as element types and attribute names. The name of a namespace is commonly used to uniquely identify each class of XML document. The unique namespaces differentiate markup elements that come from different sources and happen to have the same name.

XML Schemata provide a way to describe and validate data in an XML environment. A schema states what elements and attributes are used to describe content in an XML document, where each element is allowed, what types of text contents are allowed within it and which elements can appear within which other elements. The use of schemata ensures that the document is structured in a consistent manner. Schemata may be created by a user and generally supported by an associated markup language, such as XML. By using an XML editor, the user can manipulate the XML file and generate XML documents that adhere to the schema the user has created. XML documents may be created to adhere to one or more schemata.

Typically, word-processing documents are not understandable by external applications unless those applications are familiar with the specific structure of the document. This makes it very difficult for applications to manipulate the word-processing documents without extensive knowledge of the application. What is needed is a way to easily manipulate, create, and display documents associated with a word-processor.

SUMMARY OF THE INVENTION

The present invention is directed at providing a word-processing document in a native XML file format that may be understood by an application that understands XML, or to enable another application or service to create a rich document in XML so that the word-processing application can open it as if it was one of its own documents.

According to one aspect of the invention, a word-processor has a native XML file format. The well formed XML file fully represents the word-processor document, and fully supports the word-processor's rich formatting. Accordingly, one of the goals of such a native XML representation is have no feature losses when saving the word-processor documents in XML according to a defined XSD.

According to another aspect of the invention, there is a published XSD file that defines all the rules behind the word-processor's XML file format. The schema describes the word-processor's XML structure. The schema file mirrors the internal word-processor program while still allowing ease of use. Thus, the schema enables third party services and applications to create XML documents understandable by the word processing application.

According to yet another aspect of the invention, hints are provided within the XML associated files providing applications that understand XML a shortcut to understanding some of the features provided by the word-processor. By using the hints, the applications do not have to know all of the specific details of the internal processing of the word-processor in order to recreate a feature.

According to yet another aspect of the invention, the word-processing document is stored in a single XML file. An application will be able to fully recreate the document from this single XML file. This includes all the images and other binary data that may be present in the document. The invention provides for a way to represent all document data in a single XML file.

According to still yet another aspect of the invention, manipulation of word-processing documents may be done on computing devices that do not include the word-processor itself.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an exemplary computing device that may be used in one exemplary embodiment of the present invention;

FIG. 2 is a block diagram illustrating an exemplary environment for practicing the present invention;

FIG. 3 shows an exemplary WPML file;

FIG. 4 shows a tree view of an exemplary word-processor XML document;

FIG. 5 illustrates a block diagram of an exemplary structure of a word-processor XML document; and

FIG. 6 illustrates a process flow for interpreting a word-processor document; in accordance with aspects of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Throughout the specification and claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise.

The terms “markup language” or “ML” refer to a language for special codes within a document that specify how parts of the document are to be interpreted by an application. In a word-processor file, the markup language specifies how the text is to be formatted or laid out, whereas in an HTML document, the ML tends to specify the text's structural function (e.g., heading, paragraph, etc.)

The terms “word-processor markup language” or “WPML” refers to markup language elements that are associated with a word-processor application and a schema associated with the word-processor application. This type of ML or schema is also often called the word-processor's “native” schema or markup.

The term “element” refers to the basic unit of an ML document. The element may contain attributes, other elements, text, and other building blocks for an ML document.

The term “tag” refers to a command inserted in a document that delineates elements within an ML document. Each element can have no more than two tags: the start tag and the end tag. It is possible to have an empty element (with no content) in which case one tag is allowed.

The content between the tags is considered the element's “children” (or descendants). Hence other elements embedded in the element's content are called “child elements” or “child nodes” or the element. Text embedded directly in the content of the element is considered the element's “child text nodes”. Together, the child elements and the text within an element constitute that element's “content”.

The term “attribute” refers to an additional property set to a particular value and associated with the element. Elements may have an arbitrary number of attribute settings associated with them, including none. Attributes are used to associate additional information with an element that will not contain additional elements, or be treated as a text node.

Illustrative Operating Environment

With reference to FIG. 1, one exemplary system for implementing the invention includes a computing device, such as computing device 100. In a very basic configuration, computing device 100 typically includes at least one processing unit 102 and system memory 104. Depending on the exact configuration and type of computing device, system memory 104 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. System memory 104 typically includes an operating system 105, one or more applications 106, and may include program data 107. In one embodiment, application 106 may include a word-processor application 120 that further includes ML editor 122. This basic configuration is illustrated in FIG. 1 by those components within dashed line 108.

Computing device 100 may have additional features or functionality. For example, computing device 100 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in FIG. 1 by removable storage 109 and non-removable storage 110. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. System memory 104, removable storage 109 and non-removable storage 110 are all examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 100. Any such computer storage media may be part of device 100. Computing device 100 may also have input device(s) 112 such as keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 114 such as a display, speakers, printer, etc. may also be included. These devices are well know in the art and need not be discussed at length here.

Computing device 100 may also contain communication connections 116 that allow the device to communicate with other computing devices 118, such as over a network. Communication connection 116 is one example of communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein includes both storage media and communication media.

Word-Processor File Structure

FIG. 2 is a block diagram illustrating an exemplary environment for practicing the present invention. The exemplary environment shown in FIG. 2 is a word-processor environment 200 that includes word-processor 120, WPML file 210, WPML Schema 215, and WPML validation engine 225.

In one embodiment, word-processor 120 has its own namespace or namespaces and a schema, or a set of schemas, that is defined for use with documents associated with word-processor 120. The set of tags and attributes defined by the schema for word-processor 120 define the format of a document to such an extent that it is referred to as its own native markup language, a Word-Processor Mark-up Language (WPML). The WPML is supported by word-processor 120 and may adhere to the rules of other markup languages, such as XML, while creating further rules of its own. A WPML provides a markup language that includes rich display information that a user can solicit without the need to spend time creating the schema corresponding to the display information.

Word-processor 120 internally validates WPML file 210. When validated, the WPML elements are examined as to whether they conform to the WPML schema 215. As previously described above, a schema states what tags and attributes are used to describe content in an ML document, where each tag is allowed, and which tags can appear within other tags, ensuring that the documentation is structured the same way. Accordingly, WPML 210 is valid when structured as set forth in arbitrary WPML schema 215.

WPML validation engine 225 operates similarly to other available validation engines for ML documents. WPML validation engine 225 evaluates WPML that is in the format of the WPML validation engine 225. For example, XML elements are forwarded to an XML validation engine. In one embodiment, a greater number of validation engines may be associated with word-processor 120 for validating a greater number of ML formats.

FIG. 3 illustrates an exemplary WPML file in accordance with the present invention. WPML file 300 includes WPML elements. An element in a markup language usually includes an opening tag (indicated by a “<” and “>”), some content, and a closing tag (indicated by a “</” and “>”). In this example, tags associated with WPML include a “w:” within the tag (e.g., 302). The “w:” prefix is used as shorthand notation for the namespace associated with the element.

There are enough WPML elements for an application that understands XML to fully recreate the document from this single XML file. Hint tags may also be included that provide information to an application to help understand the content of the file. For a more complete description of the WPML used according to one embodiment of the invention, please see the description below. An exemplary WPML file that is more detailed is also discussed below.

The text contained within the document follows the “T” tag, making it easy for an application to extract the text content from a word-processing document created in accordance with aspects of the invention. Given that the example shown is valid, WPML file 210 produces a document with a body and two paragraphs that include the text “Work” in the first paragraph and “123 Main” in the second paragraph.

FIG. 4 illustrates a tree view of a word-processor document, according to aspects of the invention. The first fields within the XML document relate to document information and properties.

For example, document statistics information may be stored. This information may include, but is not limited to, title, subject, author, manager, company, category, keywords. The information may also relate do document statistics such as creation date, modification date, last access date, last print date, number ofpages, words, lines, characters, and the like. Custom properties may also be stored.

According to one embodiment of the invention, all of the fonts are defined up front. The font information includes the supporting font information.

Similarly, styles, tables, numbering, and the like are defined. The styles fields include formatting at different list levels, the type of list, and any other information needed for a list. Paragraphs contained within the XML document may point at list styles are they may default to a style.

The character style contains information that relates to the text within the word-processing document. For example the character style may include properties relating to the font style, size, color, underline style, text effects, scaling, spacing, kerning, and the like. Any character property defined by the word-processor may be included. The text of the word-processing document (“text runs”) point to the styles to define how the text should be displayed. A hint may also be provided that helps an application display the text.

The paragraph style generally includes character properties as well as paragraph properties. Paragraph properties may include paragraph alignment, outline level, indentation, spacing before and after the paragraph, line spacing, pagination properties, and the like. The paragraph section may include information such as the style name of the paragraph, the list information, and the like.

Table styles will contain a lot of information specific to the design of the table. This will include information such as banding, etc. Table properties include information such borders; width; and grid units. The Grid Units of the table is referenced by the cells to get their width.

The text node contains the actual content of the document. All of the text for the word-processing document is stored within this node. This feature makes it very easy to be able to just access the content of the document. All of the other elements may be ignored if all that is desired is the text.

Section properties contain information such as page layout, footer and header information, and other information specific to a section of the word-processor document.

The text run references the character style name as well as allowing properties.

Images and objects are within a Paragraph. Even floating ones are contained in a paragraph. When floating, this is where an anchor would appear. According to one embodiment of the invention, images are stored as a binary encoding. For an exemplary image stored as a binary encoding, please refer to the exemplary word processor file below.

Template information relating to the word processor may also be stored within the word processor document. According to one embodiment of the invention, the template information is stored as a binary encoding within the word processor document.

A paragraph mark element represents the paragraph mark. Since the paragraph mark itself can have formatting applied to it, we need to output an element to represent the paragraph mark that we can give character properties.

As can be seen by the exemplary layout of the file, an application may use as much, or as little of the information as it desires. If the application desires to recreate or create the document exactly as the word-processor would then there is sufficient information within the document to do so. If the application desires to minimally format the content, on the other hand, then the application may do that as well.

FIG. 5 illustrates a block diagram of a document, in accordance with aspects of the invention. Styles 505 include list styles 510, char styles 512, paragraph styles 514, and table styles 516. Properties 518 include document properties 520 and information properties 522. Body 524 includes exemplary section 526 and exemplary section 528. Section 526 includes paragraph 530 that includes specific property information 530 and text run 532. As can be seen, the text runs may include properties and the text or possibly an image or an object.

Exemplary section 528 includes table 550 that includes properties relating to the table and a definition of the table rows and the cells contained within the table. The sections may also include information relating to the footnotes, print information and the like.

Different parts of the document may refer to the styles (505) to define how the element will be displayed. For example, as illustrated within the figure, some paragraphs may refer to list styles 414 or paragraph styles 516. Text runs refer to char styles 412, and tables may refer to table styles 516.

The word-processor document includes all of the information within the document that allows it to be recreated an application.

Other information may also be included within the document that is not needed by the word-processing program. According to one embodiment of the invention a “hints” element is included that allows external programs to easily be able to recognize what a particular element is, or how to recreate the element. For example, a specific number format may be in a list and used by the external program to recreate the document without knowing the specifics of the style.

FIG. 6 illustrates a process 600 flow for intrepreting a word-processor document, in accordance with aspects of the invention. After a start block, the process moves to block 610, at which point the word-processor document is parsed. The parsing may include looking at the entire document, or only at specific portions of the document. For example, one application may parse the document for text only, another application may parse the document for text and images, whereas another document may desire the entire rich content within the document.

Flowing to block 615, the document is interpreted according to the published XSD. The XSD defines how to interpret the XML document created by the word-processor.

At decision block 620, a determination is made as to whether to display the document. When the document is to be displayed the process moves to block 625 where the document is displayed. The document may be displayed to a user for editing or some other purposes. When the document is not to be displayed, the process moves to decision block 630.

At decision block 630, a determination is made as to whether to modify the document. The document may be modified by a user or by the application itself with no user interaction. The document may be modified for many reasons. For example, additional text may be added or deleted, a portion of the document may be formatted differently, an image may be added, and the like. When the document is to be modified the process moves to block 635 where the document is modified (See FIG. 7 and related discussion). The document is modified in accordance with an XSD that defines all of the information needed to create a word-processor document. An exemplary XSD is described below.

As a further illustration of an exemplary word-processor document, the following is a word-processor document created in accordance with aspects of the present invention. According to one embodiment of the invention, the word-processor document is stored as a single XML document.

-   -   <?xml version=“1.0” encoding=“UTF-8” standalone=“no” ?>     -   <?mso-application progid=“Word.Document”?>

-   <w:WordDocument     xmlns:w=“schemas-microsoft:Microsoft.Word.XML.Document.1.0”     xmlns:v=“urn:schemas-microsoft-com:vml”     xmins:w10=“urn:schemas-microsoft-com:office:word”     xmlns:SL=“schemas-microsoft-schemaLibrary” xmlns:aml=“urn:aml-core”     xmins:WX=“urn:schemas-microsoft-com:office:word:aux”     xmlns:o=“urn:schemas-microsoft-com:office:office”     xmlns:US0=“resume-schema” xml:space=“preserve”>

-   <w:docInfo>

-   <w:Title w:val=“The quick brown fox jumps over the lazy dog”/>

-   <w:Author w:val=“Brian Jones”/>

-   <w:Template w:val=“Normal.dot”/>

-   <w:LastAuthor w:val=“Brian Jones”/>

-   <w:Revision w:val=“13”/>

-   <w:AppName w:val=“Microsoft Word 11.0”/>

-   <w:TotalEdit w:val=“34”/>

-   <w:Created w:val=“2002-04-10T20:26:00Z”/>

-   <w:LastSaved w:val=“2002-04-10T21:17:00Z”/>

-   <w:Pages w:val=“1”/>

-   <w:Words w:val=“138”/>

-   <w:Characters w:val=“566”/>

-   <w:Company w:val=“Microsoft Corp.”/>

-   <w:Lines w:val=“12” WX:estimate=“true”/>

-   <w:Paras w:val=“7” WX:estimate=“true”/>

-   <w:CharactersWithSpaces w:val=“697” WX:estimate=“true”/>

-   <w:Version w:val=“11.4004”/>

-   <w:CustomProp w:name=“Solution ID” w:type=“string” w:val=“None”/>

-   </w:doclnfo>

-   <w:docPr>

-   <w:View w:val=“web”/>

-   <w:T>The quick brown fox jumps o</w:T>     -   </w: r>

-   <w:r>

-   <w:T>ver the lazy dog. The quick brown fox jumps over the lazy dog.     The quick brown fox jumps over the lazy dog. The quick brown fox     jumps over the lazy dog. The quick brown fox jumps over the     lazy</w:T>     -   </w:r>

-   <w:ProofErr w:type=“spellStart”/>

-   <w:r>

-   <w:T>dog.hello</w:T>     -   </w:r>

-   <w:ProofErr w:type=“spellEnd”/>     -   </w:p>

-   <w:p/>

-   <w:p/>

-   <w:sectPr>

-   <w:PgSz w:w=“12240” w:h=“15840”/>

-   <w:PgMar w:top=“1440” w:right=“1800” w:bottom=“1440” w:left=“1800”     w:header=“720” w:footer=“720” w:gutter=“0”/>     -   </w:sectPr>     -   </WX:sub-section>     -   </WX:sect>     -   </w:body>     -   </w:WordDocument>

The word-processor document created in accordance with aspects of the invention is very rich. If desired, an application that understands XML may create and/or modify the word-processor document. The application may also ignore many of the elements within the document if so desired. For example, an application may desire to only know the text contained within the document. According to this particular example, the application would only have to extract the elements identified by the <w:T>tag.

In order for an application to understand the word-processor documents created by the word-processor, an XSD file is provided. Below is an exemplary XSD file that may be used for interpreting and/or creating the rich word-processing documents in XML.

-   <?xml version=“1.0” encoding=“UTF-8”?><xsd:schema -   targetNamespace=“urn:schemas-microso.ft-com:office:wordml-11.0” -   elementFormDefault=“qualified” attributeFormDefault=“qualified” -   xmlns:xsd=“http://www.w3.org/2001/XMLSchema”     xmlns=“urn:schemas-microsoft-com:office:wordml-11.0”     xmlns:wbld=“urn-microsoft-com-word-build” -   xmlns:WX=“urn:schemas-microsoft-com:office:wordml-11.0:aux”><xsd:import     id=“WX” namespace=“urn:schemas-microsoft-com:office:wordml-11.0:aux” -   schemaLocation=“wordnet.xsd”><xsd:import><xsd:import id=“xml” -   namespace=“http://www.w3.org/XML/1998/namespace”></xsd:import><xsd:attribute -   name=“ignore”><xsd:simpleType><xsd:restriction -   base=“xsd:string”><xsd:enumeration -   value=“tagOnly”></xsd:enumeration><xsd:enumeration -   value=“subTree”></xsd:enumeration></xsd:restriction></xsd:simpleType></xsd:attrib     ute><xsd:attribute name=“st”     type=“BooleanType”><xsd:attribute><xsd:simpleType -   name=“BooleanType”><xsd:restriction     base=“xsd:string”><xsd:enumeration -   value=“on”></xsd:enumeration><xsd:enumeration -   value=“off”>/xsd:enumeration></xsd:restriction></xsd:simpleTypexsd:complexTy -   pe name=“BooleanProperty”><xsd:attribute name=“val”     type=“BooleanType” -   default=“on”><xsd:attribute></xsd:complexType><xsd:simpleType -   name=“HexNumberType”><xsd:restriction -   base=“xsd:hexBinary”><xsd:restriction></xsd:simpleType><xsd:complexType -   name=“HexNumberProperty”><xsd:attribute name=“val”     type=“HexNumberType” -   use=“required”></xsd:attribute><xsd:complexType><xsd:simpleType -   name=“DecimalNumberType”><xsd:restriction -   base=“xsd:integer”></xsd:restriction></xsd:simpleType><xsd:complexType -   name=“DecimalNumberProperty”><xsd:attribute name=“val” -   minOccurs=“0”></xsd:element><xsd:element name=“docPr”     type=“docPrElt” -   minOccurs=“1”></xsd:element><xsd:element name=“docOleData” -   type=“BinDataProperty” minOccurs=“0”></xsd:element><xsd:element     name=“fonts” -   type=“fontsElt” minOccurs=“0”></xsd:element><xsd:element     name=“frameset” -   type=“framesetElt” minOccurs=“0”></xsd:element><xsd:element     name=“lists” -   type=“listsElt” minOccurs=“0”></xsd:element><xsd:element     name=“styles” -   type=“stylesElt” minOccurs=“0”></xsd:element><xsd:element     name=“divs” -   type=“divsElt” minOccurs=“0”></xsd:element><xsd:element     name=“docSuppData” -   type=“BinDataProperty” minOccurs=“0”></xsd:element><xsd:element -   name=“shapeDefaults” minOccurs=“0”></xsd:element><xsd:element     name=“body” -   type=“bodyElt” minOccurs=“1” -   maxOccurs=“1”><xsd:element></xsd:sequence><xsd:attribute     name=“version” -   type=“StringType” use=“optional”></xsd:attribute><xsd:attribute     ref=“xml:space” -   use=“optional”></xsd:attribute></xsd:complexType></xsd:element></xsd:schema>

As discussed above, hints may be provided within the XML associated files providing applications that understand XML a shortcut to understanding some of the features provided by the word-processor. By using the hints, the applications do not have to know all of the specific details of the internal processing of the word-processor in order to recreate a feature. Below is an exemplary hints schema, in accordance with aspects of the invention.  <?xml version=“1.0” ?> -<xsd:schema xmlns:xsd=“http://www.w3.org/2001/XMLSchema”  targetNamespace=“urn:schemas-microsoft-com:office:wordml-11.0:aux”  xmlns:wbld=“urn-microsoft-com-word-build” xmlns=“urn:schemas-microsoft-  com:office:wordml-11.0:aux” xmlns:W=“urn:schemas-microsoft-com:office:wordml-  11.0” attributeFormDefault=“qualified” elementFormDefault=“qualified”> -<xsd:element name=“sect” wbld:cname=“sect”> -<xsd:complexType> -<xsd:sequence>  <xsd:element name=“sub-section” minOccurs=“0” maxOccurs=“unbounded” />  </xsd:sequence>  </xsd:complexType>  </xsd:element> -<xsd:complexType name=“FontElt”>  <xsd:attribute name=“val” type=“xsd:string” />  </xsd:complexType>  <xsd:element name=“AllowEmptyCollapse” />  <xsd:element name=“Font” type=“FontElt” /> - <!--  BG COLOR PROPERTY  --> -<xsd:complexType name=“bgcolorType”> -<xsd:attribute name=“bgcolor”> -<xsd:simpleType> -<xsd:union> -<xsd:simpleType> -<xsd:restriction base=“xsd:hexBinary”>  <xsd:length value=“6” fixed=“true” />  </xsd:restriction>  </xsd:simpleType> -<xsd:simpleType> -<xsd:restriction base=“xsd:string”>  <xsd:enumeration value=“auto” />  </xsd:restriction>  </xsd:simpleType>  </xsd:union>  </xsd:simpleType>  </xsd:attribute>  </xsd:complexType> -<xsd:complexType name=“bdrwidthType”>  <xsd:attribute name=“bdrwidth” type=“xsd:integer” />  </xsd:complexType> - <!--  ESTIMATE PROPERTY  --> -<xsd:attribute name=“estimate”> -<xsd:simpleType> -<xsd:restriction base=“xsd:string”>  <xsd:enumeration value=“true” />  <xsd:enumeration value=“false” />  </xsd:restriction>  </xsd:simpleType>  </xsd:attribute> -<xsd:complexType name=“StringElt”>  <xsd:attribute name=“val” type=“xsd:string” />  </xsd:complexType>  <xsd:element name=“t” type=“xsd: string” />  <xsd:element name=“UIName” type=“StringElt” />  <xsd:element name=“CnfStyle” type=“StringElt” />  </xsd:schema>

The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended. 

1-31. (canceled)
 32. A method for interacting with a document, comprising: accessing the document, wherein the document is created by an application having a rich set of features and wherein the document is stored as a single well-formed XML file and includes information to recreate the document; interpreting the document using a published XSD, wherein the XSD defines the rules relating to the XML file format of the document and wherein the XSD is available to applications other than the application that created the document, and performing an action on the document, wherein the action is selected from at least one of: displaying, parsing, extracting, modifying, reading, and creating the document.
 33. The method of claim 32, wherein performing the action further comprises utilizing a hint tag within the XML file in order to understand a feature associated with the application that created the document without having to know the details of the internal processing of the application that created the document.
 34. The method of claim 32, wherein performing the action further comprises extracting style information from the XML file, wherein the style information includes at least one of a list style, a character style, a paragraph style, a section style, a numbering style, a bulleting style, and a table style.
 35. The method of claim 32, wherein performing the action further comprises parsing for non-structured feature tags that may span other features and can be recognized and parsed separately from other elements, wherein the non-structured feature tags relate to at least one of comments, bookmarks, and document protection.
 36. The method of claim 32, wherein performing the action further comprises parsing the XML file for document properties, wherein the document properties include at least three of the following: a title, an author, a template, a last author, a revision, an application name, a total number of edits, a created date, a last saved date, a pages date, a word count, a character count, a company name, a lines count, a paragraphs count, a characters with spaces count, a version, and any custom properties.
 37. The method of claim 32, wherein performing the action further comprises parsing the XML file to extract text within the document, wherein the text is contained between a start text tag and an end text tag, wherein only text is contained within the start text tag and the end text tag.
 38. The method of claim 32, wherein performing the action further comprises parsing the XML file for font information associated with the document, wherein the font information includes at least one of a font name, an alternate name, a panose name, a character set name, a family, and a pitch.
 39. The method of claim 32, wherein performing the action further comprises parsing the XML file for formatting information, wherein the formatting information contains at least one of the following: font style, size, color, shading, text effects, scaling, spacing, kerning, tabs, justification, and indents.
 40. The method of claim 32, wherein performing the action further comprises parsing the XML file for section information, wherein the section information includes at least one of the following: page layout for a section, footer information, and header information.
 41. The method of claim 32, wherein performing the action further comprises parsing the XML file for table and outline information, wherein the table information includes at least one of the following properties: borders, width, height, and grid units and wherein the outline information includes information relating to the outline style.
 42. The method of claim 32, wherein performing the action further comprises parsing the XML file for proofing information that includes at least one of a spelling state and a grammar state.
 43. A computer-readable medium having computer-executable instructions for interacting with a document, comprising: accessing the document, wherein the document is created by an application having a rich set of features and is stored as a single well-formed XML file that includes formatting information and document information relating to the document; interpreting the document using a published XSD, wherein the XSD defines the rules relating to the XML file format of the document and wherein the XSD is available to applications other than the application that created the document, and performing an action on the document, wherein the action is selected from at least one of: displaying, parsing, extracting, modifying, reading, and creating the document.
 44. The computer-readable medium of claim 43, wherein performing the action further comprises utilizing a hint tag within the XML file to recreate a feature associated with the application.
 45. The computer-readable medium of claim 43, wherein performing the action further comprises extracting style information from the XML file, wherein the style information includes at least one of a list style, a character style, a paragraph style, a section style, a numbering style, a bulleting style, and a table style.
 46. The computer-readable medium of claim 43, wherein performing the action further comprises parsing for a non-structured feature tags that may span other features and can be recognized and parsed separately from other elements, wherein the non-structured feature tags relate to at least one of comments, bookmarks, and document protection.
 47. The computer-readable medium of claim 43, wherein the document information includes a majority of the following: a title, an author, a template, a last author, a revision, an application name, a total number of edits, a created date, a last saved date, a pages date, a word count, a character count, a company name, a lines count, a paragraphs count, a characters with spaces count, a version, and custom properties.
 48. The computer-readable medium of claim 43, wherein performing the action further comprises parsing the XML file to extract all of the text within the document by extracting all of the data between start text tags and end text tags within the XML file.
 49. The computer-readable medium of claim 43, wherein performing the action further comprises parsing the XML file for font information associated with the document, wherein the font information includes at least one of a a font name, an alternate name, a panose name, a character set name, a family, and a pitch.
 50. The computer-readable medium of claim 43, wherein the formatting information contains at least one of the following: font style, size, color, shading, text effects, scaling, spacing, kerning, tabs, justification, and indents.
 51. The computer-readable medium of claim 43, wherein performing the action further comprises parsing the XML file for header and footer information.
 52. The computer-readable medium of claim 43, wherein performing the action further comprises parsing the XML file for table and outline information, wherein the table information includes at least one of the following properties: borders, width, height, and grid units and wherein the outline information includes information relating to the outline style.
 53. The computer-readable medium of claim 43, wherein performing the action further comprises parsing the XML file for proofing information relating to at least one of a spelling state and a grammar state associated with the document. 